Component org.nuxeo.ecm.core.storage.lock.LockManagerService
In bundle org.nuxeo.ecm.core.storage
Documentation
Manages Lock Managers.
Resolution Order
160
The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime
framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.
Start Order
818
The start order represents the order in which this component has been started by the Nuxeo Runtime framework.
This number is interesting to tweak if your Java component interacts with other components, and needs to be started before or after another one.
It can be changed by implementing the method "Component#getApplicationStartedOrder()" on your Java component: components are sorted according to this reference value, in increasing order.
The default value is 1000, and the repository initialization uses number 100. Negative values can also be used.
Implementation
Class:
org.nuxeo.ecm.core.storage.lock.LockManagerService
Services
Extension Points
XML Source
<?xml version="1.0"?>
<component name="org.nuxeo.ecm.core.storage.lock.LockManagerService"
version="1.0.0">
<documentation>
Manages Lock Managers.
</documentation>
<implementation
class="org.nuxeo.ecm.core.storage.lock.LockManagerService" />
<service>
<provide interface="org.nuxeo.ecm.core.storage.lock.LockManagerService" />
</service>
<extension-point name="lockmanager">
<documentation>
Extension point to register lock managers.
A new Lock Manager can be contributed using the following extension point:
<code>
<lockmanager name="default" class="some.class.implementing.LockManager" />
</code>
A repository will use the Lock Manager of the same name.
</documentation>
<object
class="org.nuxeo.ecm.core.storage.lock.LockManagerDescriptor" />
</extension-point>
</component>